Apparatus, system and method of beamforming

ABSTRACT

Some demonstrative embodiments include apparatuses, devices, systems and methods of beamforming, For example, a responder station may process a received Beam Refinement Protocol (BRP) request including a beam tracking request from an initiator station; and select whether or not to transmit a BRP response including beam tracking feedback, in response to the BRP request, based on a comparison between a. time period and a BRP tracking time limit, the time period being based on a timing of the BRP request and a timing of the BRP response.

CROSS REFERENCE

This application claims the benefit of and priority from U.S.Provisional Patent Application No. 62/144,953 entitled “Apparatus,System and Method of Beamforming”, filed Apr. 9, 2015, the entiredisclosure of which is incorporated herein by reference.

TECHNICAL FIELD

Embodiments described herein generally relate to beamforming.

BACKGROUND

A wireless communication network in a millimeter-wave band may providehigh-speed data access for users of wireless communication devices.

A beamforming procedure may be configured to steer a first directionalantenna of a first wireless communication device, e.g., a beamforminginitiator (BI), and a second directional antenna of a second wirelesscommunication device, e.g., a beamforming responder (BR). Thebeamforming procedure may be performed, for example, to establish a highthroughout communication link between the BI and the BR, e.g., at anacceptable communication range between the BR and the BI.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of a capabilities element, inaccordance with some demonstrative embodiments.

FIG. 3 is a schematic illustration of an operation element, inaccordance with some demonstrative embodiments.

FIG. 4 is a schematic flow-chart illustration of a method ofbeamforming, in accordance with some demonstrative embodiments.

FIG. 5 is a schematic illustration of a product of manufacture, inaccordance with some demonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment”, “an embodiment”, “demonstrativeembodiment”, “various embodiments” etc., indicate that the embodiment(s)so described may include a particular feature, structure, orcharacteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first”, “second”, “third” etc., to describe a common object,merely indicate that different instances of like objects are beingreferred to, and are not intended to imply that the objects so describedmust be in a given sequence, either temporally, spatially, in ranking,or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a User Equipment (UE), a Mobile Device (MD), awireless station (STA), a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, an Internet of Things (IoT) device, a sensor device, a servercomputer, a handheld computer, a handheld device, a Personal DigitalAssistant (PDA) device, a handheld PDA device, an on-board device, anoff-board device, a hybrid device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a consumer device, a non-mobile ornon-portable device, a wireless communication station, a wirelesscommunication device, a wireless Access Point (AP), a wired or wirelessrouter, a wired or wireless modem, a video device, an audio device, anaudio-video (A/V) device, a wired or wireless network, a wireless areanetwork, a Wireless Video Area Network (WVAN), a Local Area Network(LAN), a Wireless LAN (WLAN), a Personal Area Network (PAN), a WirelessPAN WPAN), and the like.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing IEEE 802.11 standards (IEEE802.11-2012, IEEE Standard for Information technology—Telecommunicationsand information exchange between systems Local and metropolitan areanetworks—Specific requirements Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications, Mar. 29, 2012;IEEE802.11ac-2013 (“IEEE P802.11ac-2013, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 4: Enhancements for Very High Throughput forOperation in Bands below 6 GHz”, December, 2013); IEEE 802.11ad (“IEEEP802.11ad-2012, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 3: Enhancements for Very High Throughput in the60 GHz Band”, 28 Dec., 2012); IEEE-802.11REVmc (“IEEE802.11-REVmc™/D3.0, June 2014 draft standard for Informationtechnology—Telecommunications and information exchange between systemsLocal and metropolitan area networks Specific requirements; Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specification”); IEEE802.11-ay (P802.11ay Standard for InformationTechnology—Telecommunications and Information Exchange Between SystemsLocal and Metropolitan Area Networks—Specific Requirements Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment: Enhanced Throughput for Operation inLicense-Exempt Bands Above 45 GHz)) and/or future versions and/orderivatives thereof, devices and/or networks operating in accordancewith existing Wireless-Gigabit-Alliance (WGA) specifications (WirelessGigabit Alliance, Inc WiGig MAC and PHY Specification Version 1.1, April2011, Final specification) and/or future versions and/or derivativesthereof, devices and/or networks operating in accordance with existingWireless Fidelity (WiFi) Alliance (WFA) Peer-to-Peer (P2P)specifications (WiFi P2P technical specification, version 1.5, Aug. 4,2014) and/or future versions and/or derivatives thereof, devices and/ornetworks operating in accordance with existing cellular specificationsand/or protocols, e.g., 3rd Generation Partnership Project (3GPP), 3GPPLong Term Evolution (LTE) and/or future versions and/or derivativesthereof, units and/or devices which are part of the above networks, andthe like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access(OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division MultipleAccess (TDMA), Multi-User MIMO (MU-MIMO), Spatial Division MultipleAccess (SDMA), Extended TDMA (E-TDMA), General Packet Radio Service(GPRS), extended GPRS, Code-Division Multiple Access (CDMA), WidebandCDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA,Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®,Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra-Wideband(UWB), Global System for Mobile communication (GSM), 2G, 2.5G, 3G, 3.5G,4G, Fifth Generation (5G), or Sixth Generation (6G) mobile networks,3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates forGSM Evolution (EDGE), or the like. Other embodiments may be used invarious other devices, systems and/or networks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a communicationsignal includes transmitting the communication signal and/or receivingthe communication signal. For example, a communication unit, which iscapable of communicating a communication signal, may include atransmitter to transmit the communication signal to at least one othercommunication unit, and/or a communication receiver to receive thecommunication signal from at least one other communication unit. Theverb communicating may be used to refer to the action of transmitting orthe action of receiving. In one example, the phrase “communicating asignal” may refer to the action of transmitting the signal by a firstdevice, and may not necessarily include the action of receiving thesignal by a second device. In another example, the phrase “communicatinga signal” may refer to the action of receiving the signal by a firstdevice, and may not necessarily include the action of transmitting thesignal by a second device.

Some demonstrative embodiments may be used in conjunction with a WLAN,e.g., a wireless fidelity (WiFi) network, and/or any other network.Other embodiments may be used in conjunction with any other suitablewireless communication network, for example, a wireless area network, a“piconet”, a WPAN, a WVAN and the like.

Some demonstrative embodiments may be used in conjunction with awireless communication network communicating over a frequency band of 60GHz. However, other embodiments may be implemented utilizing any othersuitable wireless communication frequency bands, for example, anExtremely High Frequency (EHF) band (the millimeter wave (mmWave)frequency band), e.g., a frequency band within the frequency band ofbetween 20 Ghz and 300 GHZ, a frequency band above 45 GHZ, a frequencyband below 20 GHZ, e.g., a Sub 1 GHZ (S1G) band, a 2.4GHz band, a 5GHZband, a WLAN frequency band, a WPAN frequency band, a frequency bandaccording to the WGA specification, and the like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a set of switched beam antennas, and/or thelike.

The phrases “directional multi-gigabit (DMG)” and “directional band”(DBand), as used herein, may relate to a frequency band wherein theChannel starting frequency is above 45 GHz. In one example, DMGcommunications may involve one or more directional links to communicateat a rate of multiple gigabits per second, for example, at least 1Gigabit per second, e.g., 7 Gigabit per second, or any other rate.

Some demonstrative embodiments may be implemented by a DMG STA (alsoreferred to as a “mmWave STA (mSTA)”), which may include for example, aSTA having a radio transmitter, which is capable of operating on achannel that is within the DMG band. The DMG STA may perform otheradditional or alternative functionality. Other embodiments may beimplemented by any other apparatus, device and/or station.

Reference is made to FIG. 1, which schematically illustrates a system100, in accordance with some demonstrative embodiments.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude one or more wireless communication devices. For example, system100 may include a first wireless communication device 102, and/or asecond wireless communication device 140.

In some demonstrative embodiments, devices 102 and/or 140 may includeand/or perform the functionality of one or more STAs. For example,device 102 may include at least one STA, and/or device 140 may includeat least one STA.

In some demonstrative embodiments, devices 102 and/or 140 may includeand/or perform the functionality of one or more DMG STAs. For example,device 102 may include at least one DMG STA, and/or device 140 mayinclude at least one DMG STA.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to perform the functionality of an access point (AP), e.g., aDMG AP, and/or a personal basic service set (PBSS) control point (PCP),e.g., a DMG PCP, for example, an AP/PCP STA, e.g., a DMG AP/PCP STA.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to perform the functionality of a non-AP STA, e.g., a DMGnon-AP STA, and/or a non-PCP STA, e.g., a DMG non-PCP STA, for example,a non-AP/PCP STA, e.g., a DMG non-AP/PCP STA.

In other embodiments, devices 102 and/or 140 may perform thefunctionality of any other additional or alternative device and/orstation.

In one example, a station (STA) may include a logical entity that is asingly addressable instance of a medium access control (MAC) andphysical layer (PHY) interface to the wireless medium (WM). The STA mayperform any other additional or alternative functionality.

In one example, an AP may include an entity that contains a station(STA), e.g., one STA, and provides access to distribution services, viathe wireless medium (WM) for associated STAs. The AP may perform anyother additional or alternative functionality.

In one example, a personal basic service set (PBSS) control point (PCP)may include an entity that contains a STA, e.g., one station (STA), andcoordinates access to the wireless medium (WM) by STAs that are membersof a PBSS. The PCP may perform any other additional or alternativefunctionality.

In one example, a PBSS may include a directional multi-gigabit (DMG)basic service set (BSS) that includes, for example, one PBSS controlpoint (PCP). For example, access to a distribution system (DS) may notbe present, but, for example, an intra-PBSS forwarding service mayoptionally be present.

In one example, a PCP/AP STA may include a station (STA) that is atleast one of a PCP or an AP. The PCP/AP STA may perform any otheradditional or alternative functionality.

In one example, a non-AP STA may include a STA that is not containedwithin an AP. The non-AP STA may perform any other additional oralternative functionality.

In one example, a non-PCP STA may include a STA that is not a PCP. Thenon-PCP STA may perform any other additional or alternativefunctionality.

In one example, a non PCP/AP STA may include a STA that is not a PCP andthat is not an AP. The non-PCP/AP STA may perform any other additionalor alternative functionality.

In some demonstrative embodiments, devices 102 and/or 140 may include amobile device or a non-mobile, e.g., a static, device. For example,devices 102 and/or 140 may include, for example, a UE, an MD, a STA, anAP, a PC, a desktop computer, a mobile computer, a laptop computer, anUltrabook™ computer, a notebook computer, a tablet computer, an Internetof Things (IoT) device, a sensor device, a server computer, a handheldcomputer, a handheld device, a PDA device, a handheld PDA device, anon-board device, an off-board device, a hybrid device (e.g., combiningcellular phone functionalities with PDA device functionalities), aconsumer device, a vehicular device, a non-vehicular device, a mobile orportable device, a non-mobile or non-portable device, a mobile phone, acellular telephone, a PCS device, a PDA device which incorporates awireless communication device, a mobile or portable GPS device, a DVBdevice, a relatively small computing device, a non-desktop computer, a“Carry Small Live Large” (CSLL) device, an Ultra Mobile Device (UMD), anUltra Mobile PC (UMPC), a Mobile Internet Device (MID), an “Origami”device or computing device, a device that supports DynamicallyComposable Computing (DCC), a context-aware device, a video device, anaudio device, an A/V device, a Set-Top-Box (STB), a Blu-ray disc (BD)player, a BD recorder, a Digital Video Disc (DVD) player, a HighDefinition (HD) DVD player, a DVD recorder, a HD DVD recorder, aPersonal Video Recorder (PVR), a broadcast HD receiver, a video source,an audio source, a video sink, an audio sink, a stereo tuner, abroadcast radio receiver, a flat panel display, a Personal Media Player(PMP), a digital video camera (DVC), a digital audio player, a speaker,an audio receiver, an audio amplifier, a gaming device, a data source, adata sink, a Digital Still camera (DSC), a media player, a Smartphone, atelevision, a music player, or the like.

In some demonstrative embodiments, device 102 may include, for example,one or more of a processor 191, an input unit 192, an output unit 193, amemory unit 194, and/or a storage unit 195; and/or device 140 mayinclude, for example, one or more of a processor 181, an input unit 182,an output unit 183, a memory unit 184, and/or a storage unit 185.Devices 102 and/or 140 may optionally include other suitable hardwarecomponents and/or software components. In some demonstrativeembodiments, some or all of the components of one or more of devices 102and/or 140 may be enclosed in a common housing or packaging, and may beinterconnected or operably associated using one or more wired orwireless links. In other embodiments, components of one or more ofdevices 102 and/or 140 may be distributed among multiple or separatedevices.

In some demonstrative embodiments, processor 191 and/or processor 181may include, for example, a Central Processing Unit (CPU), a DigitalSignal Processor (DSP), one or more processor cores, a single-coreprocessor, a dual-core processor, a multiple-core processor, amicroprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 191 executes instructions,for example, of an Operating System (OS) of device 102 and/or of one ormore suitable applications. Processor 181 executes instructions, forexample, of an Operating System (OS) of device 140 and/or of one or moresuitable applications.

In some demonstrative embodiments, input unit 192 and/or input unit 182may include, for example, a keyboard, a keypad, a mouse, a touch-screen,a touch-pad, a track-ball, a stylus, a microphone, or other suitablepointing device or input device. Output unit 193 and/or output unit 183includes, for example, a monitor, a screen, a touch-screen, a flat paneldisplay, a Light Emitting Diode (LED) display unit, a Liquid CrystalDisplay (LCD) display unit, a plasma display unit, one or more audiospeakers or earphones, or other suitable output devices.

In some demonstrative embodiments, memory unit 194 and/or memory unit184 may include, for example, a Random Access Memory (RAM), a Read OnlyMemory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flashmemory, a volatile memory, a non-volatile memory, a cache memory, abuffer, a short term memory unit, a long term memory unit, or othersuitable memory units. Storage unit 195 and/or storage unit 185includes, for example, a hard disk drive, a floppy disk drive, a CompactDisk (CD) drive, a CD-ROM drive, a DVD drive, or other suitableremovable or non-removable storage units. Memory unit 194 and/or storageunit 195, for example, may store data processed by device 102. Memoryunit 184 and/or storage unit 185, for example, may store data processedby device 140.

In some demonstrative embodiments, wireless communication devices 102and/or 140 may be capable of communicating content, data, informationand/or signals via a wireless medium (WM) 103. In some demonstrativeembodiments, wireless medium 103 may include, for example, a radiochannel, a cellular channel, an RF channel, a Wireless Fidelity (WiFi)channel, an IR channel, a Bluetooth (BT) channel, a Global NavigationSatellite System (GNSS) Channel, and the like.

In some demonstrative embodiments, WM 103 may include a directionalchannel. For example, WM 103 may include a millimeter-wave (mmWave)wireless communication channel.

In some demonstrative embodiments, WM 103 may include a DMG channel. Inother embodiments WM 103 may include any other directional channel.

In other embodiments, WM 103 may include any other additional oralternative type of channel over any other frequency band.

In some demonstrative embodiments, devices 102 and/or 140 may includeone or more radios including circuitry and/or logic to perform wirelesscommunication between devices 102, 140 and/or one or more other wirelesscommunication devices. For example, device 102 may include a radio 114,and/or device 140 may include a radio 144.

In some demonstrative embodiments, radios 114 and/or 144 may include oneor more wireless receivers (Rx) including circuitry and/or logic toreceive wireless communication signals, RF signals, frames, blocks,transmission streams, packets, messages, data items, and/or data. Forexample, radio 114 may include a receiver 116, and/or radio 144 mayinclude a receiver 146.

In some demonstrative embodiments, radios 114 and/or 144 may include oneor more wireless transmitters (Tx) including circuitry and/or logic tosend wireless communication signals, RF signals, frames, blocks,transmission streams, packets, messages, data items, and/or data. Forexample, radio 114 may include a transmitter 118, and/or radio 144 mayinclude a transmitter 148.

In some demonstrative embodiments, radios 114 and/or 144 may includecircuitry, logic, modulation elements, demodulation elements,amplifiers, analog to digital and digital to analog converters, filters,and/or the like. For example, radios 114 and/or 144 may include or maybe implemented as part of a wireless Network Interface Card (NIC), andthe like.

In some demonstrative embodiments, radios 114 and/or 144 may include, ormay be associated with, one or more antennas 107 and/or 147,respectively.

In one example, device 102 may include a single antenna 107. In otherexample, device 102 may include two or more antennas 107.

In one example, device 140 may include a single antenna 147. In otherexample, device 140 may include two or more antennas 147.

Antennas 107 and/or 147 may include any type of antennas suitable fortransmitting and/or receiving wireless communication signals, blocks,frames, transmission streams, packets, messages and/or data. Forexample, antennas 107 and/or 147 may include any suitable configuration,structure and/or arrangement of one or more antenna elements,components, units, assemblies and/or arrays. Antennas 107 and/or 147 mayinclude, for example, antennas suitable for directional communication,e.g., using beamforming techniques. For example, antennas 107 and/or 147may include a phased array antenna, a multiple element antenna, a set ofswitched beam antennas, and/or the like. In some embodiments, antennas107 and/or 147 may implement transmit and receive functionalities usingseparate transmit and receive antenna elements. In some embodiments,antennas 107 and/or 147 may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements.

In some demonstrative embodiments, antennas 107 and/or 147 may include adirectional antenna, which may be steered to a plurality of beamdirections. For example, antenna 107 may be steered to a plurality ofbeam directions 135, and/or antenna 147 may be steered to a plurality ofbeam directions 145.

In some demonstrative embodiments, devices 102 and/or 140 may select apair of beams including a first beam direction of the plurality of beamdirections 135, e.g., including a direction 133, and a second beamdirection of the plurality of beam directions 145, e.g., including adirection 143, to communicate between devices 102 and 140, for example,via a mmWave wireless communication link and/or any other link.

In some demonstrative embodiments, device 102 may include a controller124, and/or device 140 may include a controller 154. Controllers 124and/or 154 may be configured to perform one or more functionalities,communications, operations and/or procedures, for example, including oneor more beamforming functionalities, communications, operations and/orprocedures between devices 102 and/or 140 and/or one or more otherdevices, e.g., as described below.

In some demonstrative embodiments, controllers 124 and/or 154 mayinclude circuitry and/or logic, e.g., one or more processors includingcircuitry and/or logic, memory circuitry and/or logic, Media-AccessControl (MAC) circuitry and/or logic, Physical Layer (PHY) circuitryand/or logic, and/or any other circuitry and/or logic, configured toperform the functionality of controllers 124 and/or 154, respectively.Additionally or alternatively, one or more functionalities ofcontrollers 124 and/or 154 may be implemented by logic, which may beexecuted by a machine and/or one or more processors, e.g., as describedbelow.

In one example, controller 124 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause a wireless device, e.g., device 102, and/or a wireless station,e.g., a wireless STA implemented by device 102, to perform one or moreoperations, communications and/or functionalities, e.g., as describedherein.

In one example, controller 154 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause a wireless device, e.g., device 140, and/or a wireless station,e.g., a wireless STA implemented by device 140, to perform one or moreoperations, communications and/or functionalities, e.g., as describedherein.

In some demonstrative embodiments, device 102 may include a messageprocessor 128 configured to generate, process and/or access one ormessages communicated by device 102.

In one example, message processor 128 may be configured to generate oneor more messages to be transmitted by device 102, and/or messageprocessor 128 may be configured to access and/or to process one or moremessages received by device 102, e.g., as described below. In oneexample, message processor 128 may be configured to process transmissionof one or more messages from a wireless station, e.g., a wireless STAimplemented by device 102; and/or message processor 128 may beconfigured to process reception of one or more messages by a wirelessstation, e.g., a wireless STA implemented by device 102.

In some demonstrative embodiments, device 140 may include a messageprocessor 158 configured to generate, process and/or access one ormessages communicated by device 140.

In one example, message processor 158 may be configured to generate oneor more messages to be transmitted by device 140, and/or messageprocessor 158 may be configured to access and/or to process one or moremessages received by device 140, e.g., as described below. In oneexample, message processor 158 may be configured to process transmissionof one or more messages from a wireless station, e.g., a wireless STAimplemented by device 140; and/or message processor 158 may beconfigured to process reception of one or more messages by a wirelessstation, e.g., a wireless STA implemented by device 140.

In some demonstrative embodiments, message processors 128 and/or 158 mayinclude circuitry, e.g., processor circuitry, memory circuitry,Media-Access Control (MAC) circuitry, Physical Layer (PHY) circuitry,and/or any other circuitry, configured to perform the functionality ofmessage processors 128 and/or 158. Additionally or alternatively, one ormore functionalities of message processors 128 and/or 158 may beimplemented by logic, which may be executed by a machine and/or one ormore processors, e.g., as described below.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of radio 114, and/or atleast part of the functionality of message processor 158 may beimplemented as part of radio 144.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of controller 124,and/or at least part of the functionality of message processor 158 maybe implemented as part of controller 154.

In other embodiments, the functionality of message processor 128 may beimplemented as part of any other element of device 102, and/or thefunctionality of message processor 158 may be implemented as part of anyother element of device 104.

In some demonstrative embodiments, at least part of the functionality ofcontroller 124 and/or message processor 128 may be implemented by anintegrated circuit, for example, a chip, e.g., a System in Chip (SoC).In one example, the chip or SoC may be configured to perform one or morefunctionalities of radio 114. For example, the chip or SoC may includeone or more elements of controller 124, one or more elements of messageprocessor 128, and/or one or more elements of radio 114.

In one example, controller 124, message processor 128, and radio 114 maybe implemented as part of the chip or SoC.

In other embodiments, controller 124, message processor 128 and/or radio114 may be implemented by one or more additional or alternative elementsof device 102.

In some demonstrative embodiments, at least part of the functionality ofcontroller 154 and/or message processor 158 may be implemented by anintegrated circuit, for example, a chip, e.g., a SoC. In one example,the chip or SoC may be configured to perform one or more functionalitiesof radio 144. For example, the chip or SoC may include one or moreelements of controller 154, one or more elements of message processor158, and/or one or more elements of radio 144. In one example,controller 154, message processor 158, and radio 144 may be implementedas part of the chip or SoC.

In other embodiments, controller 154, message processor 158 and/or radio144 may be implemented by one or more additional or alternative elementsof device 140.

In some demonstrative embodiments, system 100 may include a beamforminginitiator (BI) and a beamforming responder (BR) to perform beamformingbetween the BI and the BR. For example, wireless communication device102 may perform the functionality of the BI, and/or wirelesscommunication device 140 may perform the functionality of the BR.

In other embodiments, wireless communication device 140 may perform thefunctionality of the BI, and/or wireless communication device 102 mayperform the functionality of the BR.

In some demonstrative embodiments, devices 102 and/or 140 may perform aBeamforming procedure (also refereed to as “beamforming trainingprotocol”) including a Sector level sweep (SLS) phase, e.g., including,for example, an Initiator Sector Sweep (ISS), which may include, forexample, a sector sweep performed, for example, by the Beamforminginitiator; and/or a responder sector sweep (RSS), which may include, forexample, a sector sweep performed, for example, by the Beamformingresponder. The RSS may, for example, follow the ISS.

In some demonstrative embodiments, devices 102 and/or 140 may opt toperform a Beam Refinement Phase (also referred to as “Beam RefinementProtocol”) (BRP), e.g., following the SLS phase.

Some demonstrative embodiments are described herein with respect to aBRP, which may be performed after a SLS phase of a beamformingprocedure. However, in other embodiments, a BRP may be performed as partof any other phase and/or procedure.

In some demonstrative embodiments, devices 102 and/or 140 may exchange aplurality of BRP frames during the BRP. For example, device 102 may sendone or more BRP frames 139, e.g., a plurality of BRP frames 139, todevice 140, and/or device 140 may send one or more BRP frames 149, e.g.,a plurality of BRP frames 149, to device 102.

In some demonstrative embodiments, one of devices 102 and/or 140 mayperform the functionality of a BRP tracking initiator (“BRP initiator”),e.g., to initiate the exchange of BRP frames 139 and 149; and/or anotherone of devices 102 and/or 140 may perform the functionality of a BRPtracking responder (“BRP responder”).

In one example, device 102 may perform the functionality of the BRPinitiator and/or device 140 may perform the functionality of the BRPresponder. In another example, device 140 may perform the functionalityof the BRP initiator and/or device 102 may perform the functionality ofthe BRP responder.

In some demonstrative embodiments, a BRP frame of BRP frames 139 and/or149, e.g., each BRP frame except a first BRP frame or only some of theframes, may be both a request for training and a response for training.

In some demonstrative embodiments, devices 102 and/or 140 may continuethe training process, for example, by continuing to perform the BRP,e.g., until at least one of devices 102 and 140, e.g., both devices 102and 140, do not require further beamforming training.

In some demonstrative embodiments, the Beam Refinement Protocol (BRP)may implement a beam tracking mechanism, which may allow, for example,ongoing refinement of an established beam link during data traffic.

In some demonstrative embodiments, a first wireless station, e.g., awireless station implemented by one of devices 102 and/or 140, mayperform the functionality of a beam tracking initiator, e.g., to send aBRP tracking request (“BRP request”) frame including a beam trackingrequest; and a second wireless station, e.g., a wireless stationimplemented by another one of devices 102 and/or 140 may perform thefunctionality of a beam tracking responder, e.g., to send a BRP trackingresponse (“BRP response”) frame including beam tracking feedback.

In one example, device 102 may perform the functionality of the beamtracking initiator and/or device 140 may perform the functionality ofthe beam tracking responder.

In some demonstrative embodiments, a BRP request may be communicated inthe form of a BRP frame, e.g., from the beam tracking initiator to thebeam tracking responder. The BRP frame may include a Physical LayerConvergence Protocol (PLCP) Protocol Data Unit (PPDU) including arequest (“request for beam tracking”) to the beam tracking responder totransmit beam tracking feedback information (“beam tracking feedback”).

In one example, controller 124 may be configured to cause an initiatorstation, e.g., a beam tracking initiator, for example, a wireless STAimplemented by device 102, to generate and transmit a BRP frameincluding the request for beam tracking, e.g., as described below.

In one example, controller 154 may be configured to cause a responderstation, e.g., a beam tracking responder, for example, a wireless STAimplemented by device 140, to process reception of the BRP frameincluding the request for beam tracking, e.g., as described below.

In some demonstrative embodiments, a BRP response may be communicated inthe form of a BRP frame, e.g., from the beam tracking responder to thebeam tracking initiator. The BRP frame may include a PPDU including thebeam tracking feedback.

In one example, controller 154 may be configured to cause the responderstation, e.g., the beam tracking responder, for example, the wirelessSTA implemented by device 140, to generate and transmit a BRP frameincluding the beam tracking feedback, e.g., as described below.

In one example, controller 124 may be configured to cause the initiatorstation, e.g., a beam tracking initiator, for example, the wireless STAimplemented by device 102, to process reception of the BRP frameincluding the beam tracking feedback, e.g., as described below.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to control, limit and/or restrict a time difference between aBRP request and a BRP response, e.g., in response to the BRP request,e.g., as described below.

In some demonstrative embodiments, the BRP response may be ready to besent by the responder, for example, when the BRP request has beenprocessed and ready to be sent, e.g., independently of any initiatorsequence and/or in a separate link access.

In some demonstrative embodiments, a late BRP response, e.g., a BRPresponse received a long time period after the BRP request, may beinadequate, e.g., for use by the beam tracking initiator, for example,due to potential changes in link conditions. Accordingly, using beamtracking feedback of a late BRP response may lead, for example, to wrongantenna configuration and/or performance loss.

In some demonstrative embodiments, a BRP response may potentially be alate BRP response, for example, when the BRP response is sent in aseparate link access. In other embodiments, a late BRP response maypotentially occur in any other additional or alternative situations,implementations and/or scenarios.

In some demonstrative embodiments, construction of a responding BRPframe may take time, which may be, for example, longer than the transmitsequence of the beam tracking initiator. Accordingly, the responding BRPframe may not be sent in the transmit sequence.

Some demonstrative embodiments may be implemented, for example, at leastwith respect to a BRP tracking response, which may be sent by the beamtracking responder, for example, in a separate link access, e.g.,separate from a channel access sequence of a link access in which a BRPrequest may be sent from the beam tracking initiator to the beamtracking responder. There is no known solution that may resolve thisscenario. For example, at least this case may not be addressed by acurrent beam tracking mechanism of a current protocol and/orSpecification, for example, the IEEE 802.11ad-2012 Specification.

In some demonstrative embodiments, a BRP response sent by a separatelink access may be different, for example, from a BRP response, whichmay be sent inside a channel access sequence. For example, the time ofthe BRP response in the separate link access may be unpredictable, e.g.,due to the separate link access.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured, for example, to provide timing control to validate a BRPtracking response to a BRP tracking request, and/or advertising of atimeout parameter, e.g., as described below.

In some demonstrative embodiments, providing the timing control tovalidate the BRP tracking response to a beam tracking request, and/oradvertising the timeout parameter may, for example, resolve the issue ofthe unpredictable BRP response, e.g., as described below.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to communicate and/or process BRP requests and/or BRPresponses according to a scheme, which may be configured, for example,at least to resolve unpredictability of the BRP response to the beamtracking request, e.g., if the BRP response is sent by a separate linkaccess, e.g., as described below.

In some demonstrative embodiments, devices 102 and/or 140 may beconfigured to communicate and/or process one or more BRP request framesand/or one or more BRP response frames, for example, based at least on aBRP tracking time limit (also referred to as“dot11BRPTrackingTimeLimit”).

In some demonstrative embodiments, the BRP tracking time limit may bedetermined, defined and/or set by a wireless station, e.g., as describedbelow.

In some demonstrative embodiments, the BRP tracking time limit may bedetermined, defined and/or set by the BRP tracking initiator and/or theBRP tracking responder, e.g., as described below.

In some demonstrative embodiments, the BRP tracking time limit may benegotiated between the BRP tracking initiator and/or the BRP trackingresponder, e.g., as described below.

In some demonstrative embodiments, the BRP tracking time limit may benegotiated between first and second peer stations, for example, peerstations establishing a beamformed link (beam link), e.g., as describedbelow.

In some demonstrative embodiments, a wireless station, e.g., thewireless station implemented by device 102 and/or the wireless stationimplemented by device 140, may be configured to communicate a messageincluding a BRP tracking time limit value, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station implemented by device 102 to transmit amessage including a first BRP tracking time limit value of the wirelessstation implemented by device 102, e.g., as described below.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station implemented by device 140 to transmit amessage including a second BRP tracking time limit value of the wirelessstation implemented by device 140, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station implemented by device 102 to process themessage from device 140 including the second BRP tracking time limitvalue, and to determine the BRP tracking time limit to be used, forexample, in a BRP between devices 102 and 140, based on at least one ofthe first and second BRP tracking time limit values, e.g., as describedbelow.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station implemented by device 102 to determine theBRP tracking time limit to be used, for example, in the BRP betweendevices 102 and 140, based on the first BRP tracking time limit valuetransmitted by device 102, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station implemented by device 102 to determine theBRP tracking time limit to be used, for example, in the BRP betweendevices 102 and 140, based on the second BRP tracking time limit valuereceived from device 140, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station implemented by device 102 to determine theBRP tracking time limit to be used, for example, in the BRP betweendevices 102 and 140, based on a comparison between the first and secondBRP tracking time limit values, e.g., as described below.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station implemented by device 140 to process themessage from device 102 including the first BRP tracking time limitvalue, and to determine the BRP tracking time limit to be used, forexample, in the BRP between devices 102 and 140, based on at least oneof the first and second BRP tracking time limit values, e.g., asdescribed below.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station implemented by device 140 to determine theBRP tracking time limit to be used, for example, in the BRP betweendevices 102 and 140, based on the second BRP tracking time limit valuetransmitted by device 140, e.g., as described below.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station implemented by device 140 to determine theBRP tracking time limit to be used, for example, in the BRP betweendevices 102 and 140, based on the first BRP tracking time limit valuereceived from device 102, e.g., as described below.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station implemented by device 140 to determine theBRP tracking time limit to be used, for example, in the BRP betweendevices 102 and 140, based on a comparison between the first and secondBRP tracking time limit values, e.g., as described below.

In some demonstrative embodiments, a wireless station, e.g., thewireless station implemented by device 102 and/or the wireless stationimplemented by device 140, may be configured to transmit the BRPtracking time limit value corresponding to the wireless station as partof a capabilities element, for example, a DMG Capabilities element,e.g., as described below.

In some demonstrative embodiments, a wireless station, e.g., thewireless station implemented by device 102 and/or the wireless stationimplemented by device 140, may be configured to transmit the BRPtracking time limit value corresponding to the wireless station as partof any other element, information element, field, subfield, and/ormessage.

Reference is made to FIG. 2, which schematically illustrates acapabilities element 200, in accordance with some demonstrativeembodiments.

In some demonstrative embodiments, capabilities element 200 may includea DMG Capabilities element, or any other capabilities element.

In some demonstrative embodiments, device 102 (FIG. 1) and/or device 140(FIG. 1) may be configured to process transmission and/or reception ofcapabilities element 200.

In one example, device 102 (FIG. 1) may be configured to generate andtransmit a message including capabilities element 200 includinginformation corresponding to device 102 (FIG. 1), for example, duringbeam link establishment or at any other time.

In another example, device 102 (FIG. 1) may be configured to processreception of a message including capabilities element 200 includinginformation corresponding to a sender of the message, e.g., device 140,for example, during beam link establishment or at any other time.

In one example, device 140 (FIG. 1) may be configured to generate andtransmit a message including capabilities element 200 includinginformation corresponding to device 140 (FIG. 1), for example, duringbeam link establishment or at any other time.

In another example, device 140 (FIG. 1) may be configured to processreception of a message including capabilities element 200 includinginformation corresponding to a sender of the message, e.g., device 102(FIG. 1), for example, during beam link establishment or at any othertime.

In some demonstrative embodiments, capabilities element 200 may includea tracking time limit subfield 220, e.g., a DMG STA BeamTrakingTimeLimitsubfield, e.g., including 2 bit octets or any other number of bits.

In some demonstrative embodiments, tracking time limit subfield 220 mayinclude, for example, a BRP tracking time limit value, e.g., a value ofdot11BeamTrackingTimeLimit, for example, corresponding to and/or set bya wireless station sending capabilities element 200.

In some demonstrative embodiments, tracking time limit subfield 220 mayinclude the BRP tracking time limit value, for example, in units of 1microsecond (us), or any other units.

In some demonstrative embodiments, tracking time limit subfield 220 maybe, for example, defined by one or more attributes and/or parameters,e.g., as follows:

dot11BeamTrackingTimeLimit OBJECT-TYPE SYNTAX Unsigned32 (0 . . . 65535)UNITS 1us MAX-ACCESS read-write STATUS current DESCRIPTION “This is acontrol variable. It is written by the MAC or SME. Changes take effectas soon as practical in the implementation. BRP tracking Initiator TimeLimit (in units of 1us).” DEFVAL { 10000 } ::= {dot11DMGBeamformingConfigEntry 11 }

In some demonstrative embodiments, capabilities element 200 may alsoinclude an Element Identifier (ID) field 202, e.g., including 1 bitoctet, a length field 204, e.g., including 1 bit octet, a STA addressfield 206, e.g., including 6 bit octets, an Association ID (AID) field208, e.g., including 1 bit octet, a DMG STA Capability information field210, e.g., including 2 bit octets, and/or a DMG AP or PCP STA Capabilityinformation field 212, e.g., including 2 bit octets.

In some demonstrative embodiments, first and second peer stations, e.g.,the STA implemented by device 102 (FIG. 1) and/or the STA implemented bydevice 140 (FIG. 1), may negotiate a value of the BRP tracking timelimit, e.g., the value of dot11BeamTrackingTimeLimit, to be used, forexample, with respect to a beam link established between the peerstations.

In some demonstrative embodiments, a first STA, denoted STA A, and asecond STA, denoted STA B, may determine the value of the BRP trackingtime limit, e.g., the value of dot11BeamTrackingTimeLimit, to be used,for example, with respect to a beam link established between STA A andSTA B, for example, based on a first BRP tracking time limit value (“DMGSTA BeamTrackingTimeLimit (STA-A)”) corresponding to the STA A, and asecond BRP tracking time limit value (“DMG STA BeamTrackingTimeLimit(STA-B)”) corresponding to the STA B. For example, the STA A maytransmit a capabilities element, e.g., capabilities element 200,including the first BRP tracking time limit value; and/or the STA B maytransmit a capabilities element, e.g., capabilities element 200,including the second BRP tracking time limit value.

In some demonstrative embodiments, the STA-A and the STA-B may includeany of the peer STAs performing a Beam Tracking Time Limit negotiationprocedure, e.g., in no particular order.

In some demonstrative embodiments, the wireless STA implemented bydevice 102 (FIG. 1) may perform the functionality of the STA A, and/orthe wireless STA implemented by device 140 (FIG. 1) may perform thefunctionality of the STA B.

In some demonstrative embodiments, a STA may set the BRP tracking timelimit value, e.g., the value in subfield 220, in a capabilities element,e.g., capabilities element 200, sent by the station to indicate whetheror not the use of BRP tracking time limit is supported by the STA,and/or to indicate a preference of the BRP tracking time limit.

In one example, the STA may set the BRP tracking time limit value, e.g.,the value in subfield 220, to a predefined value, e.g., “0” or any othervalue, to indicate that the use of BRP tracking time limit is notsupported by the STA, and/or that the STA is not to use the BRP timetracking limit.

In one example, the STA may set the BRP tracking time limit value, e.g.,the value in subfield 220, to a value within a predefined range ofvalues, e.g., a value greater than zero and less than 65535 or any otherrange, to indicate a BRP tracking time limit of the STA, e.g., a BRPtracking time limit preferred by the STA.

In one example, the STA may set the BRP tracking time limit value, e.g.,the value in subfield 220, to a predefined value, e.g., 65535 or anyother value, to indicate that the STA has no preference with respect tothe BRP tracking time limit, and/or that the BRP tracking time limit maybe set to any value in the range.

In some demonstrative embodiments, the STA A and the STA B may determinethe BRP tracking time limit, e.g., the value ofdot11BeamTrackingTimeLimit, to be used, for example, with respect to abeam link established between the peer stations, e.g., as follows:

TABLE 1 DMG STA DMG STA Beam Beam dot11BeamTrackingTimeLimit TrackingTracking (STA-A) vs. TimeLimit TimeLimit dot11BeamTrackingTimeLimit(STA-A) (STA-B) (STA-B) Result 0 0 NA Beam >0 0 NA tracking is 0 >0 NAnot supported >0 and >0 and >, = dot11Beam <65535 <65535 TrackingTimeLimit (STA-A) >0 and >0 and < dot11Beam <65535 <65535 TrackingTimeLimit (STA-B) 65535 >0 and NA dot11Beam <65535 Tracking TimeLimit(STA-B) >0 and 65535 NA dot11Beam <65535 Tracking TimeLimit (STA-A)65535 65535 NA Default dot11Beam Tracking TimeLimit value

In some demonstrative embodiments, the value of he BRP tracking timelimit may be communicated between peer STAs, for example, usingcapabilities element 200, e.g., as described above.

In other demonstrative embodiments, the value of he BRP tracking timelimit value may be determined, set and/or defined by a PCP/AP STA, e.g.,for one or more STAs associated with the PCP/AP STA, e.g., as describedbelow.

In some demonstrative embodiments, while associated with AP/PCP STA, aSTA may override the value of dot11BRPTrackingTimeLimit with the valueof the BRPTrackingTimeLimit subfield, for example, when the STA receivesthis element from the AP/PCP STA.

In some demonstrative embodiments, the AP/PCP STA may generate andtransmit an operation element, e.g., a DMG operation element, includinga BRP tracking time limit subfield.

In some demonstrative embodiments, a non-PCP/AP STA may receive theoperation element from the PAP/AP STA, and may use a BRP tracking timelimit value in accordance with the BRP tracking time limit subfield, forexample, with respect to a beam link with another non-PCP/AP STA.

Reference is made to FIG. 3, which schematically illustrates anoperation element 300, in accordance with some demonstrativeembodiments.

In some demonstrative embodiments, operation element 300 may include aDMG Operation element, or any other operation element.

In some demonstrative embodiments, device 102 (FIG. 1) and/or device 140(FIG. 1) may be configured to process transmission and/or reception ofoperation element 300.

In some demonstrative embodiments, operation element 300 may include atracking time limit subfield 320, e.g., a DMG STA BeamTrakingTimeLimitsubfield, e.g., including 2 bit octets.

In some demonstrative embodiments, tracking time limit subfield 320 mayinclude, for example, a BRP tracking time limit value, e.g., a value ofdot11BeamTrackingTimeLimit, for example, as may be set by a wirelessstation sending operation element 300, e.g., a PCP/AP STA.

In some demonstrative embodiments, operation element 320 may alsoinclude, for example, an element ID subfield 302, a length subfield 304,a DMG Operation Information subfield 306, and/or a DMG BSS ParameterConfiguration subfield 308, and/or any other subfield.

Referring back to FIG. 1, in some demonstrative embodiments, controller124 may be configured to cause an initiator station, e.g., a beamtracking initiator station implemented by device 102, to communicateand/or process one or more BRP frames, e.g., with a responder station,during a BRP, for example, based on a BRP tracking time limit, e.g., asdescribed below.

In some demonstrative embodiments, controller 140 may be configured tocause a responder station, e.g., a beam tracking responder stationimplemented by device 140, to communicate and/or process one or more BRPframes, e.g., with the initiator station, during the BRP, for example,based on the BRP tracking time limit, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to determine the BRP tracking time limit,for example, based at least on a BRP tracking time limit valuetransmitted by the initiator station, e.g., as described above.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to determine the BRP tracking time limit,for example, based at least on a BRP tracking time limit valuetransmitted by the responder station, e.g., as described above.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to determine the BRP tracking time limit,for example, based at least on a BRP tracking time limit value receivedfrom the responder station, e.g., as described above.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to determine the BRP tracking time limit,for example, based at least on a BRP tracking time limit value receivedfrom the initiator station, e.g., as described above.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to negotiate the BRP tracking time limitwith the responder station, e.g., as described below.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to negotiate the BRP tracking time limitwith the initiator station, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to transmit a first capabilities element,e.g., capabilities element 200 (FIG. 2), including a first BRP trackingtime limit value, e.g., in BRP tracking time limit subfield 220 (FIG.2), e.g., as described above.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to process the first capabilities elementincluding the first BRP tracking time limit value from the initiatorstation.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to transmit a second capabilities element,e.g., capabilities element 200 (FIG. 2), including a second BRP trackingtime limit value, e.g., in BRP tracking time limit subfield 220 (FIG.2), e.g., as described above.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to process the second capabilities elementincluding the second BRP tracking time limit value from the responderstation.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to determine the BRP tracking time limitbased on the first and second BRP tracking time limit values; and/orcontroller 154 may be configured to cause the responder station todetermine the BRP tracking time limit based on the first and second BRPtracking time limit values.

In some demonstrative embodiments, controllers 124 and/or 154 may beconfigured to determine the BRP tracking time limit based on acomparison between the first and second BRP tracking time limit values,e.g., according to Table 1 and/or according to any other conditionsand/or criteria.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to transmit a BRP request including a beamtracking request to the responder station.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to transmit the BRP request, for example, ifat least one of the following conditions is met:

-   -   a time duration since transmission of a last BRP request to the        responder station is greater than a sum of the BRP tracking time        limit and a predefined time period, for example, a protocol        inter-frame space (PIFS), e.g., a beam refinement protocol        inter-frame space (BRPIFS); and    -   a previous BRP response was received from the responder station.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to transmit the BRP request, for example,only if at least one of these conditions is met. For example, controller124 may be configured to select not to cause the initiator station,e.g., the beam tracking initiator station implemented by device 102, totransmit the BRP request, e.g., if both of these conditions are not met.

In other embodiments, controller 124 may be configured to cause theinitiator station to transmit the BRP request based on any otheradditional or alternative conditions and/or criteria.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to process reception of the BRP requestincluding the beam tracking request from the initiator station.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to prepare a beam tracking response, e.g.,including measurement feedback, to be sent to the beam tracking request.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to select whether or not to transmit a BRPresponse including beam tracking feedback, e.g., the measurementfeedback, in response to the BRP request, for example, based on acomparison between a time period and the BRP tracking time limit.

In some demonstrative embodiments, the time period may be based on atiming of the BRP request and a timing of the BRP response. For example,the time period may be between the timing of the BRP request and atiming of the BRP response.

In some demonstrative embodiments, the timing of the BRP request may bebased, for example, on a Physical Layer (PHY) Receive (Rx) end(PHY-RXEND) indication primitive of the BRP request.

In some demonstrative embodiments, the timing of the BRP response may bebased, for example, on a Physical Layer (PHY) Transmit (Tx) end(PHY-TXEND) indication primitive of the BRP response.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to transmit the BRP response, for example,when the time period is equal to or less than the BRP tracking timelimit.

In some demonstrative embodiments, controller 154 may be configured tocause the responder station to select not to transmit the BRP response,for example, when the time period is longer than the BRP tracking timelimit.

For example, controller 154 may be configured to cause the responderstation to select not to transmit the BRP response, when a time periodbetween the PHY-RXEND indication primitive of the BRP request and thePH-TXEND indication primitive of the BRP response is longer than the BRPtracking time limit.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to select whether or not beam trackingfeedback in the BRP response from the responder station is to beprocessed as a response to the beam tracking request, based on acomparison between a time period and a BRP tracking time limit.

In some demonstrative embodiments, the time period may be based on atiming of the BRP request and a timing of the BRP response.

In some demonstrative embodiments, the timing of the BRP request may bebased, for example, on a PHY-TXEND indication primitive of the BRPrequest.

In some demonstrative embodiments, the timing of the BRP response isbased on a PHY-RXEND indication primitive of the BRP response.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to process the feedback in the BRP response,for example, when the time period is less than the BRP tracking timelimit.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to select to ignore the feedback in the BRPresponse, for example, when the time period is equal to or greater thanthe BRP tracking time limit.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to determine a failure of the beam trackingrequest, when the BRP response is not received within the BRP trackingtime limit.

In some demonstrative embodiments, controller 124 may be configured tocause the initiator station to operate during a BRP, and/or controller154 may be configured to cause the responder station to operate duringthe BRP, for example, according to one or more, e.g., some or all, ofthe operations and/or conditions described below.

In some demonstrative embodiments, a beam tracking initiator maytransmit to the beam tracking responder a PPDU requesting to transmitbeam tracking, if at least one of the following conditions is met:

-   -   the time duration since the last PPDU it transmitted to the beam        tracking responder that requested transmit beam tracking is        greater than dot11Beam TrackingTimeLimit plus BRPIFS,    -   a BRP frame with the channel measurement feedback from the beam        tracking responder has been received.

In some demonstrative embodiments, if the beam tracking initiator doesnot receive the expected feedback from the beam tracking responderwithin a time period that is less than dot11BeamTrackingTimeLimit of thelast request, the beam tracking initiator may consider the beam trackingrequest as failed.

In some demonstrative embodiments, if the initiator receives theexpected feedback from the responder within time that is greater than orequal to dot11Beam TrackingTimeLimit of the last request, the beamtracking initiator should ignore it.

In some demonstrative embodiments, the time of arrival of the beamtracking responder's feedback may be indicated by thePHY-RXEND.indication primitive of the PPDU that contains the BRP MACManagement Protocol Data Unit (MMPDU).

In some demonstrative embodiments, the time of transmit completion ofthe beam tracking initiator's PPDU may be indicated by thePHY-TXEND.confirm primitive.

In some demonstrative embodiments, the beam tracking responder shall nottransmit a BRP frame with feedback to the beam tracking initiator if thetime period between PHY-RXEND.indication primitive of the PPDU thatcontains the beam tracking request and of PHY-TXEND.confirm primitive ofthe response BRP frame is longer than dot11BeamTrackingTimeLimit.

Reference is made to FIG. 4, which schematically illustrates a method ofbeamforming, in accordance with some demonstrative embodiments. Forexample, one or more of the operations of the method of FIG. 4 may beperformed by one or more elements of a system, e.g., system 100 (FIG.1), for example, one or more wireless devices, e.g., device 102 (FIG. 1)and/or device 140 (FIG. 1), a controller, e.g., controller 124 (FIG. 1)and/or controller 154 (FIG. 1), a radio, e.g., radio 114 (FIG. 1) and/orradio 144 (FIG. 1), and/or a message processor, e.g., message processor128 (FIG. 1) and/or message processor 158 (FIG. 1).

As indicated at block 402, the method may include transmitting a BRPrequest including a beam tracking request to a responder station. Forexample, controller 124 (FIG. 1) may cause device 102 (FIG. 1) totransmit the BRP request, e.g., as described above.

As indicated at block 404, the method may include processing a receivedBRP request including a beam tracking request from an initiator station.For example, controller 154 (FIG. 1) may cause device 140 (FIG. 1) toprocess reception of the BRP request, e.g., as described above.

As indicated at block 406, the method may include selecting whether ornot to transmit a BRP response including beam tracking feedback, inresponse to the BRP request, based on a comparison between a time periodand a BRP tracking time limit, the time period being based on a timingof the BRP request and a timing of the BRP response. For example,controller 154 (FIG. 1) may cause device 140 (FIG. 1) to select whetheror not to transmit the BRP response, for example, based on the BRPtracking time limit, e.g., as described above.

As indicated at block 408, the method may include selecting whether ornot beam tracking feedback in the BRP response from the responderstation is to be processed as a response to the beam tracking request,based on a comparison between a time period and the BRP tracking timelimit, the time period being based on a timing of the BRP request and atiming of the BRP response. For example, controller 124 (FIG. 1) maycause device 102 (FIG. 1) to select whether or not to process the beamtracking feedback in the BRP response, for example, based on the BRPtracking time limit, e.g., as described above.

Reference is made to FIG. 5, which schematically illustrates a productof manufacture 500, in accordance with some demonstrative embodiments.Product 500 may include a non-transitory machine-readable storage medium502 to store logic 504, which may be used, for example, to perform atleast part of the functionality of devices 102 and/or 140 (FIG. 1),transmitters 118 and/or 148 (FIG. 1), receivers 116 and/or 146 (FIG. 1),controllers 124 and/or 154 (FIG. 1), and/or message processors 128(FIG. 1) and/or 158 (FIG. 1), and/or to perform one or more operationsof the method of FIG. 4. The phrase “non-transitory machine-readablemedium” is directed to include all computer-readable media, with thesole exception being a transitory propagating signal.

In some demonstrative embodiments, product 500 and/or machine-readablestorage medium 502 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 902 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 504 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 504 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like.

The instructions may include any suitable type of code, such as sourcecode, compiled code, interpreted code, executable code, static code,dynamic code, and the like. The instructions may be implementedaccording to a predefined computer language, manner or syntax, forinstructing a processor to perform a certain function. The instructionsmay be implemented using any suitable high-level, low-level,object-oriented, visual, compiled and/or interpreted programminglanguage, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC,assembly language, machine code, and the like.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising circuitry configured to causea responder station to process a received Beam Refinement Protocol (BRP)request comprising a beam tracking request from an initiator station;and select whether or not to transmit a BRP response comprising beamtracking feedback, in response to the BRP request, based on a comparisonbetween a time period and a BRP tracking time limit, the time periodbeing based on a timing of the BRP request and a timing of the BRPresponse.

Example 2 includes the subject mater of Example 1, and optionally, beingconfigured to cause the responder station to transmit the BRP response,when the time period is equal to or less than the BRP tracking timelimit.

Example 3 includes the subject mater of Example 1 or 2, and optionally,being configured to cause the responder station to select not totransmit the BRP response, when the time period is longer than the BRPtracking time limit.

Example 4 includes the subject mater of any one of Examples 1-3, andoptionally, being configured to cause the responder station to determinethe BRP tracking time limit based at least on a BRP tracking time limitvalue transmitted by the responder station.

Example 5 includes the subject mater of any one of Examples 1-4, andoptionally, being configured to cause the responder station to determinethe BRP tracking time limit based at least on a BRP tracking time limitvalue received from the initiator station.

Example 6 includes the subject mater of any one of Examples 1-5, andoptionally, being configured to cause the responder station to negotiatethe BRP tracking time limit with the initiator station.

Example 7 includes the subject mater of any one of Examples 1-6, andoptionally, being configured to cause the responder station to transmita first capabilities element comprising a first BRP tracking time limitvalue, to process a second capabilities element comprising a second BRPtracking time limit value from the initiator station, and to determinethe BRP tracking time limit based on the first and second BRP trackingtime limit values.

Example 8 includes the subject mater of Example 7, and optionally, beingconfigured to cause the responder station to determine the BRP trackingtime limit based on a comparison between the first and second BRPtracking time limit values.

Example 9 includes the subject mater of any one of Examples 1-8,andoptionally, wherein the timing of the BRP request is based on a PhysicalLayer (PHY) Receive (Rx) end (PHY-RXEND) indication primitive of the BRPrequest.

Example 10 includes the subject mater of any one of Examples 1-9,andoptionally, wherein the timing of the BRP response is based on aPhysical Layer (PHY) Transmit (Tx) end (PHY-TXEND) indication primitiveof the BRP response.

Example 11 includes the subject mater of any one of Examples 1-10,andoptionally, wherein the responder station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 12 includes the subject mater of any one of Examples 1-11, andoptionally, comprising a radio to receive the BRP request and totransmit the BRP response.

Example 13 includes the subject mater of any one of Examples 1-12, andoptionally, comprising one or more antennas, a memory and a processor.

Example 14 includes an apparatus comprising circuitry configured tocause an initiator station to transmit a Beam Refinement Protocol (BRP)request comprising a beam tracking request to a responder station; andselect whether or not beam tracking feedback in a BRP response from theresponder station is to be processed as a response to the beam trackingrequest, based on a comparison between a time period and a BRP trackingtime limit, the time period being based on a timing of the BRP requestand a timing of the BRP response.

Example 15 includes the subject mater of Example 14, and optionally,being configured to cause the initiator station to transmit the BRPrequest if at least one of the following conditions is met: a timeduration since transmission of a last BRP request to the responderstation is greater than a sum of the BRP tracking time limit and a beamrefinement protocol inter-frame space (BRPIFS); and a previous BRPresponse was received from the responder station.

Example 16 includes the subject mater of Example 14 or 15, andoptionally, being configured to cause the initiator station to processthe feedback in the BRP response, when the time period is less than theBRP tracking time limit.

Example 17 includes the subject mater of Example 14 or 15, andoptionally, being configured to cause the initiator station to select toignore the feedback in the BRP response, when the time period is equalto or greater than the BRP tracking time limit.

Example 18 includes the subject mater of any one of Examples 14-17, andoptionally, being configured to cause the initiator station to determinea failure of the beam tracking request, when the BRP response is notreceived within the BRP tracking time limit.

Example 19 includes the subject mater of any one of Examples 14-18, andoptionally, being configured to cause the initiator station to determinethe BRP tracking time limit based at least on a BRP tracking time limitvalue transmitted by the initiator station.

Example 20 includes the subject mater of any one of Examples 14-19, andoptionally, being configured to cause the initiator station to determinethe BRP tracking time limit based at least on a BRP tracking time limitvalue received from the responder station.

Example 21 includes the subject mater of any one of Examples 14-20, andoptionally, being configured to cause the initiator station to negotiatethe BRP tracking time limit with the responder station.

Example 22 includes the subject mater of any one of Examples 14-21, andoptionally, being configured to cause the initiator station to transmita first capabilities element comprising a first BRP tracking time limitvalue, to process a second capabilities element comprising a second BRPtracking time limit value from the responder station, and to determinethe BRP tracking time limit based on the first and second BRP trackingtime limit values.

Example 23 includes the subject mater of Example 22, and optionally,being configured to cause the initiator station to determine the BRPtracking time limit based on a comparison between the first and secondBRP tracking time limit values.

Example 24 includes the subject mater of any one of Examples 14-23, andoptionally, wherein the timing of the BRP request is based on a PhysicalLayer (PHY) Transmit (Tx) end (PHY-TXEND) indication primitive of theBRP request.

Example 25 includes the subject mater of any one of Examples 14-24, andoptionally, wherein the timing of the BRP response is based on aPhysical Layer (PHY) Receive (Rx) end (PHY-RXEND) indication primitiveof the BRP response.

Example 26 includes the subject mater of any one of Examples 14-25, andoptionally, wherein the responder station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 27 includes the subject mater of any one of Examples 14-26, andoptionally, comprising a radio to transmit the BRP request and toreceive the BRP response.

Example 28 includes the subject mater of any one of Examples 14-27, andoptionally, comprising one or more antennas, a memory and a processor.

Example 29 includes a method to be performed at a responder station, themethod comprising processing a received Beam Refinement Protocol (BRP)request comprising a beam tracking request from an initiator station;and selecting whether or not to transmit a BRP response comprising beamtracking feedback, in response to the BRP request, based on a comparisonbetween a time period and a BRP tracking time limit, the time periodbeing based on a timing of the BRP request and a timing of the BRPresponse.

Example 30 includes the subject mater of Example 29, and optionally,comprising transmitting the BRP response, when the time period is equalto or less than the BRP tracking time limit.

Example 31 includes the subject mater of Example 29 or 30, andoptionally, comprising selecting not to transmit the BRP response, whenthe time period is longer than the BRP tracking time limit.

Example 32 includes the subject mater of any one of Examples 29-31, andoptionally, comprising determining the BRP tracking time limit based atleast on a BRP tracking time limit value transmitted by the responderstation.

Example 33 includes the subject mater of any one of Examples 29-32, andoptionally, comprising determining the BRP tracking time limit based atleast on a BRP tracking time limit value received from the initiatorstation.

Example 34 includes the subject mater of any one of Examples 29-33, andoptionally, comprising negotiating the BRP tracking time limit with theinitiator station.

Example 35 includes the subject mater of any one of Examples 29-34, andoptionally, comprising transmitting a first capabilities elementcomprising a first BRP tracking time limit value, processing a secondcapabilities element comprising a second BRP tracking time limit valuefrom the initiator station, and determining the BRP tracking time limitbased on the first and second BRP tracking time limit values.

Example 36 includes the subject mater of Example 35, and optionally,comprising determining the BRP tracking time limit based on a comparisonbetween the first and second BRP tracking time limit values.

Example 37 includes the subject mater of any one of Examples 29-36, andoptionally, wherein the timing of the BRP request is based on a PhysicalLayer (PHY) Receive (Rx) end (PHY-RXEND) indication primitive of the BRPrequest.

Example 38 includes the subject mater of any one of Examples 29-37, andoptionally, wherein the timing of the BRP response is based on aPhysical Layer (PHY) Transmit (Tx) end (PHY-TXEND) indication primitiveof the BRP response.

Example 39 includes the subject mater of any one of Examples 29-38, andoptionally, wherein the responder station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 40 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at a responder station, the operationscomprising processing a received Beam Refinement Protocol (BRP) requestcomprising a beam tracking request from an initiator station; andselecting whether or not to transmit a BRP response comprising beamtracking feedback, in response to the BRP request, based on a comparisonbetween a time period and a BRP tracking time limit, the time periodbeing based on a timing of the BRP request and a timing of the BRPresponse.

Example 41 includes the subject mater of Example 40, and optionally,wherein the operations comprise transmitting the BRP response, when thetime period is equal to or less than the BRP tracking time limit.

Example 42 includes the subject mater of Example 40 or 41, andoptionally, wherein the operations comprise selecting not to transmitthe BRP response, when the time period is longer than the BRP trackingtime limit.

Example 43 includes the subject mater of any one of Examples 40-42, andoptionally, wherein the operations comprise determining the BRP trackingtime limit based at least on a BRP tracking time limit value transmittedby the responder station.

Example 44 includes the subject mater of any one of Examples 40-43, andoptionally, wherein the operations comprise determining the BRP trackingtime limit based at least on a BRP tracking time limit value receivedfrom the initiator station.

Example 45 includes the subject mater of any one of Examples 40-44, andoptionally, wherein the operations comprise negotiating the BRP trackingtime limit with the initiator station.

Example 46 includes the subject mater of any one of Examples 40-45, andoptionally, wherein the operations comprise transmitting a firstcapabilities element comprising a first BRP tracking time limit value,processing a second capabilities element comprising a second BRPtracking time limit value from the initiator station, and determiningthe BRP tracking time limit based on the first and second BRP trackingtime limit values.

Example 47 includes the subject mater of Example 46, and optionally,wherein the operations comprise determining the BRP tracking time limitbased on a comparison between the first and second BRP tracking timelimit values.

Example 48 includes the subject mater of any one of Examples 40-47, andoptionally, wherein the timing of the BRP request is based on a PhysicalLayer (PHY) Receive (Rx) end (PHY-RXEND) indication primitive of the BRPrequest.

Example 49 includes the subject mater of any one of Examples 40-48, andoptionally, wherein the timing of the BRP response is based on aPhysical Layer (PHY) Transmit (Tx) end (PHY-TXEND) indication primitiveof the BRP response.

Example 50 includes the subject mater of any one of Examples 40-49, andoptionally, wherein the responder station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 51 includes an apparatus of wireless communication by aresponder station, the apparatus comprising means for processing areceived Beam Refinement Protocol (BRP) request comprising a beamtracking request from an initiator station; and means for selectingwhether or not to transmit a BRP response comprising beam trackingfeedback, in response to the BRP request, based on a comparison betweena time period and a BRP tracking time limit, the time period being basedon a timing of the BRP request and a timing of the BRP response.

Example 52 includes the subject mater of Example 51, and optionally,comprising means for transmitting the BRP response, when the time periodis equal to or less than the BRP tracking time limit.

Example 53 includes the subject mater of Example 51 or 52, andoptionally, comprising means for selecting not to transmit the BRPresponse, when the time period is longer than the BRP tracking timelimit.

Example 54 includes the subject mater of any one of Examples 51-53, andoptionally, comprising means for determining the BRP tracking time limitbased at least on a BRP tracking time limit value transmitted by theresponder station.

Example 55 includes the subject mater of any one of Examples 51-54, andoptionally, comprising means for determining the BRP tracking time limitbased at least on a BRP tracking time limit value received from theinitiator station.

Example 56 includes the subject mater of any one of Examples 51-55, andoptionally, comprising means for negotiating the BRP tracking time limitwith the initiator station.

Example 57 includes the subject mater of any one of Examples 51-56, andoptionally, comprising means for transmitting a first capabilitieselement comprising a first BRP tracking time limit value, processing asecond capabilities element comprising a second BRP tracking time limitvalue from the initiator station, and determining the BRP tracking timelimit based on the first and second BRP tracking time limit values.

Example 58 includes the subject mater of Example 57comprising means fordetermining the BRP tracking time limit based on a comparison betweenthe first and second BRP tracking time limit values.

Example 59 includes the subject mater of any one of Examples 51-58, andoptionally, wherein the timing of the BRP request is based on a PhysicalLayer (PHY) Receive (Rx) end (PHY-RXEND) indication primitive of the BRPrequest.

Example 60 includes the subject mater of any one of Examples 51-59, andoptionally, wherein the timing of the BRP response is based on aPhysical Layer (PHY) Transmit (Tx) end (PHY-TXEND) indication primitiveof the BRP response.

Example 61 includes the subject mater of any one of Examples 51-60, andoptionally, wherein the responder station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 62 includes a method to be performed at an initiator station,the method comprising transmitting a Beam Refinement Protocol (BRP)request comprising a beam tracking request to a responder station; andselecting whether or not beam tracking feedback in a BRP response fromthe responder station is to be processed as a response to the beamtracking request, based on a comparison between a time period and a BRPtracking time limit, the time period being based on a timing of the BRPrequest and a timing of the BRP response.

Example 63 includes the subject mater of Example 62, and optionally,comprising transmitting the BRP request if at least one of the followingconditions is met: a time duration since transmission of a last BRPrequest to the responder station is greater than a sum of the BRPtracking time limit and a beam refinement protocol inter-frame space(BRPIFS); and a previous BRP response was received from the responderstation.

Example 64 includes the subject mater of Example 62 or 63, andoptionally, comprising processing the feedback in the BRP response, whenthe time period is less than the BRP tracking time limit.

Example 65 includes the subject mater of Example 62 or 63, andoptionally, comprising selecting to ignore the feedback in the BRPresponse, when the time period is equal to or greater than the BRPtracking time limit.

Example 66 includes the subject mater of any one of Examples 62-65, andoptionally, comprising determining a failure of the beam trackingrequest, when the BRP response is not received within the BRP trackingtime limit.

Example 67 includes the subject mater of any one of Examples 62-66, andoptionally, comprising determining the BRP tracking time limit based atleast on a BRP tracking time limit value transmitted by the initiatorstation.

Example 68 includes the subject mater of any one of Examples 62-67, andoptionally, comprising determining the BRP tracking time limit based atleast on a BRP tracking time limit value received from the responderstation.

Example 69 includes the subject mater of any one of Examples62-68comprising negotiating the BRP tracking time limit with theresponder station.

Example 70 includes the subject mater of any one of Examples 62-69, andoptionally, comprising transmitting a first capabilities elementcomprising a first BRP tracking time limit value, processing a secondcapabilities element comprising a second BRP tracking time limit valuefrom the responder station, and determining the BRP tracking time limitbased on the first and second BRP tracking time limit values.

Example 71 includes the subject mater of Example 70, and optionally,comprising determining the BRP tracking time limit based on a comparisonbetween the first and second BRP tracking time limit values.

Example 72 includes the subject mater of any one of Examples 62-71, andoptionally, wherein the timing of the BRP request is based on a PhysicalLayer (PHY) Transmit (Tx) end (PHY-TXEND) indication primitive of theBRP request.

Example 73 includes the subject mater of any one of Examples 62-72, andoptionally, wherein the timing of the BRP response is based on aPhysical Layer (PHY) Receive (Rx) end (PHY-RXEND) indication primitiveof the BRP response.

Example 74 includes the subject mater of any one of Examples 62-73, andoptionally, wherein the responder station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 75 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at an initiator station, the operationscomprising transmitting a Beam Refinement Protocol (BRP) requestcomprising a beam tracking request to a responder station; and selectingwhether or not beam tracking feedback in a BRP response from theresponder station is to be processed as a response to the beam trackingrequest, based on a comparison between a time period and a BRP trackingtime limit, the time period being based on a timing of the BRP requestand a timing of the BRP response.

Example 76 includes the subject mater of Example 75, and optionally,wherein the operations comprise transmitting the BRP request if at leastone of the following conditions is met: a time duration sincetransmission of a last BRP request to the responder station is greaterthan a sum of the BRP tracking time limit and a beam refinement protocolinter-frame space (BRPIFS); and a previous BRP response was receivedfrom the responder station.

Example 77 includes the subject mater of Example 75 or 76, andoptionally, wherein the operations comprise processing the feedback inthe BRP response, when the time period is less than the BRP trackingtime limit.

Example 78 includes the subject mater of Example 75 or 76, andoptionally, wherein the operations comprise selecting to ignore thefeedback in the BRP response, when the time period is equal to orgreater than the BRP tracking time limit.

Example 79 includes the subject mater of any one of Examples 75-78, andoptionally, wherein the operations comprise determining a failure of thebeam tracking request, when the BRP response is not received within theBRP tracking time limit.

Example 80 includes the subject mater of any one of Examples 75-79, andoptionally, wherein the operations comprise determining the BRP trackingtime limit based at least on a BRP tracking time limit value transmittedby the initiator station.

Example 81 includes the subject mater of any one of Examples 75-80, andoptionally, wherein the operations comprise determining the BRP trackingtime limit based at least on a BRP tracking time limit value receivedfrom the responder station.

Example 82 includes the subject mater of any one of Examples 75-81, andoptionally, wherein the operations comprise negotiating the BRP trackingtime limit with the responder station.

Example 83 includes the subject mater of any one of Examples 75-82, andoptionally, wherein the operations comprise transmitting a firstcapabilities element comprising a first BRP tracking time limit value,processing a second capabilities element comprising a second BRPtracking time limit value from the responder station, and determiningthe BRP tracking time limit based on the first and second BRP trackingtime limit values.

Example 84 includes the subject mater of Example 83, and optionally,wherein the operations comprise determining the BRP tracking time limitbased on a comparison between the first and second BRP tracking timelimit values.

Example 85 includes the subject mater of any one of Examples 75-84, andoptionally, wherein the timing of the BRP request is based on a PhysicalLayer (PHY) Transmit (Tx) end (PHY-TXEND) indication primitive of theBRP request.

Example 86 includes the subject mater of any one of Examples 75-85, andoptionally, wherein the timing of the BRP response is based on aPhysical Layer (PHY) Receive (Rx) end (PHY-RXEND) indication primitiveof the BRP response.

Example 87 includes the subject mater of any one of Examples 75-86, andoptionally, wherein the responder station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 88 includes an apparatus of wireless communication by aninitiator station, the apparatus comprising means for transmitting aBeam Refinement Protocol (BRP) request comprising a beam trackingrequest to a responder station; and means for selecting whether or notbeam tracking feedback in a BRP response from the responder station isto be processed as a response to the beam tracking request, based on acomparison between a time period and a BRP tracking time limit, the timeperiod being based on a timing of the BRP request and a timing of theBRP response.

Example 89 includes the subject mater of Example 88, and optionally,comprising means for transmitting the BRP request if at least one of thefollowing conditions is met: a time duration since transmission of alast BRP request to the responder station is greater than a sum of theBRP tracking time limit and a beam refinement protocol inter-frame space(BRPIFS); and a previous BRP response was received from the responderstation.

Example 90 includes the subject mater of Example 88 or 89, andoptionally, comprising means for processing the feedback in the BRPresponse, when the time period is less than the BRP tracking time limit.

Example 91 includes the subject mater of Example 88 or 89, andoptionally, comprising means for selecting to ignore the feedback in theBRP response, when the time period is equal to or greater than the BRPtracking time limit.

Example 92 includes the subject mater of any one of Examples 88-91, andoptionally, comprising means for determining a failure of the beamtracking request, when the BRP response is not received within the BRPtracking time limit.

Example 93 includes the subject mater of any one of Examples 88-92, andoptionally, comprising means for determining the BRP tracking time limitbased at least on a BRP tracking time limit value transmitted by theinitiator station.

Example 94 includes the subject mater of any one of Examples 88-93, andoptionally, comprising means for determining the BRP tracking time limitbased at least on a BRP tracking time limit value received from theresponder station.

Example 95 includes the subject mater of any one of Examples 88-94, andoptionally, comprising means for negotiating the BRP tracking time limitwith the responder station.

Example 96 includes the subject mater of any one of Examples 88-95, andoptionally, comprising means for transmitting a first capabilitieselement comprising a first BRP tracking time limit value, processing asecond capabilities element comprising a second BRP tracking time limitvalue from the responder station, and determining the BRP tracking timelimit based on the first and second BRP tracking time limit values.

Example 97 includes the subject mater of Example 96, and optionally,comprising means for determining the BRP tracking time limit based on acomparison between the first and second BRP tracking time limit values.

Example 98 includes the subject mater of any one of Examples 88-97, andoptionally, wherein the timing of the BRP request is based on a PhysicalLayer (PHY) Transmit (Tx) end (PHY-TXEND) indication primitive of theBRP request.

Example 99 includes the subject mater of any one of Examples 88-98, andoptionally, wherein the timing of the BRP response is based on aPhysical Layer (PHY) Receive (Rx) end (PHY-RXEND) indication primitiveof the BRP response.

Example 100 includes the subject mater of any one of Examples 88-99, andoptionally, wherein the responder station is a Directional Multi-Gigabit(DMG) Station (STA).

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features have been illustrated and described herein, manymodifications, substitutions, changes, and equivalents may occur tothose skilled in the art. It is, therefore, to be understood that theappended claims are intended to cover all such modifications and changesas fall within the true spirit of the disclosure.

What is claimed is:
 1. An apparatus comprising: memory circuitry; and aprocessor comprising logic and circuitry configured to cause a beamtracking initiator wireless communication station (STA) to: determine abeam tracking time limit based on a value in a beam tracking time limitfield from a beam tracking responder STA; transmit a Physical layer(PHY) Protocol Data Unit (PPDU) to the beam tracking responder STA, thePPDU comprising a beam tracking request; and determine that the beamtracking request has failed, based on a determination that a BeamRefinement Protocol (BRP) frame comprising feedback is not received fromthe beam tracking responder STA within a time period, that is less thanthe beam tracking time limit, from the PPDU comprising the beam trackingrequest.
 2. The apparatus of claim 1 configured to cause the beamtracking initiator STA to ignore the feedback from the beam trackingresponder STA, based on a determination that the BRP frame comprisingthe feedback is received after a time period, that is equal to orgreater than the beam tracking time limit, from the PPDU comprising thebeam tracking request.
 3. The apparatus of claim 1 configured to allowthe beam tracking initiator STA to transmit the PPDU comprising the beamtracking request, based on a determination that a time duration sincetransmission of a last PPDU to the beam tracking responder STAcomprising a request for beam tracking is greater than a sum of the beamtracking time limit and a beam refinement protocol inter-frame space(BRPIFS).
 4. The apparatus of claim 1 configured to allow the beamtracking initiator STA to transmit the PPDU comprising the beam trackingrequest, based on a determination that a previous BRP frame withfeedback was received from the beam tracking responder STA.
 5. Theapparatus of claim 1, wherein the time period is between a PHY Transmit(Tx) end confirm (PHY-TXEND.confirm) primitive of the PPDU and a PHYReceive (Rx) end indication (PHY-RXEND.indication) primitive of the BRPframe.
 6. The apparatus of claim 1 configured to cause the beam trackinginitiator STA to determine the beam tracking time limit based on a firsttime limit value and a second time limit value, the first time limitvalue comprising the value in the beam tracking time limit field fromthe beam tracking responder STA, the second time limit valuecorresponding to the beam tracking initiator STA.
 7. The apparatus ofclaim 6 configured to cause the beam tracking initiator STA to determinethe beam tracking time limit based on a comparison between the firsttime limit value and the second time limit value.
 8. The apparatus ofclaim 6 configured to cause the beam tracking initiator STA to determinethe beam tracking time limit according to the first time limit value,based on a determination that the first time limit value is greater than0 and less than 65535, the second time limit value is greater than 0 andless than 65535, and the first time limit value is equal to or greaterthan the second time limit value.
 9. The apparatus of claim 6 configuredto cause the beam tracking initiator STA to determine the beam trackingtime limit according to the second time limit value, based on adetermination that the first time limit value is greater than 0 and lessthan 65535, the second time limit value is greater than 0 and less than65535, and the second time limit value is greater than the first timelimit value.
 10. The apparatus of claim 6 configured to cause the beamtracking initiator STA to determine the beam tracking time limitaccording to the first time limit value, based on a determination thatthe first time limit value is greater than 0 and less than 65535, andthe second time limit value is
 65535. 11. The apparatus of claim 6configured to cause the beam tracking initiator STA to determine thebeam tracking time limit according to the second time limit value, basedon a determination that the first time limit value is 65535, and thesecond time limit value is greater than 0 and less than
 65535. 12. Theapparatus of claim 6 configured to cause the beam tracking initiator STAto determine the beam tracking time limit according to a default timelimit value, based on a determination that the first time limit value is65535 and the second time limit value is
 65535. 13. The apparatus ofclaim 1, wherein the beam tracking time limit field is in a DirectionalMulti-Gigabit (DMG) capabilities element from the beam trackingresponder STA.
 14. The apparatus of claim 1, wherein the beam trackingtime limit field has a size of two octets.
 15. The apparatus of claim 1,wherein the beam tracking initiator STA comprises a DirectionalMulti-Gigabit (DMG) STA.
 16. The apparatus of claim 1 comprising aradio, the processor configured to cause the radio to transmit the PPDU.17. The apparatus of claim 16 comprising one or more antennas connectedto the radio, and another processor to execute instructions of anoperating system.
 18. A product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone processor, enable the at least one processor to cause a beamtracking initiator wireless communication station (STA) to: determine abeam tracking time limit based on a value in a beam tracking time limitfield from a beam tracking responder STA; transmit a Physical layer(PHY) Protocol Data Unit (PPDU) to the beam tracking responder STA, thePPDU comprising a beam tracking request; and determine that the beamtracking request has failed, based on a determination that a BeamRefinement Protocol (BRP) frame comprising feedback is not received fromthe beam tracking responder STA within a time period, that is less thanthe beam tracking time limit, from the PPDU comprising the beam trackingrequest.
 19. The product of claim 18, wherein the instructions, whenexecuted, cause the beam tracking initiator STA to ignore the feedbackfrom the beam tracking responder STA, based on a determination that theBRP frame comprising the feedback is received after a time period, thatis equal to or greater than the beam tracking time limit, from the PPDUcomprising the beam tracking request.
 20. The product of claim 18,wherein the instructions, when executed, allow the beam trackinginitiator STA to transmit the PPDU comprising the beam tracking request,based on a determination that a time duration since transmission of alast PPDU to the beam tracking responder STA comprising a request forbeam tracking is greater than a sum of the beam tracking time limit anda beam refinement protocol inter-frame space (BRPIFS).
 21. The productof claim 18, wherein the instructions, when executed, allow the beamtracking initiator STA to transmit the PPDU comprising the beam trackingrequest, based on a determination that a previous BRP frame withfeedback was received from the beam tracking responder STA.
 22. Anapparatus for a beam tracking initiator wireless communication station(STA), the apparatus comprising: means for determining a beam trackingtime limit based on a value in a beam tracking time limit field from abeam tracking responder STA; means for causing the beam trackinginitiator STA to transmit a Physical layer (PHY) Protocol Data Unit(PPDU) to the beam tracking responder STA, the PPDU comprising a beamtracking request; and means for determining that the beam trackingrequest has failed, based on a determination that a Beam RefinementProtocol (BRP) frame comprising feedback is not received from the beamtracking responder STA within a time period, that is less than the beamtracking time limit, from the PPDU comprising the beam tracking request.23. The apparatus of claim 22 comprising means for causing the beamtracking initiator STA to ignore the feedback from the beam trackingresponder STA, based on a determination that the BRP frame comprisingthe feedback is received after a time period, that is equal to orgreater than the beam tracking time limit, from the PPDU comprising thebeam tracking request.